Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 08c735dcee40f44bcc24319d4f0f625c4fb8a049ccd1f591bc8365a32ed7d2cc

Tx prefix hash: 8977083ea9e33298effa8dcd675a4be7710905d36f919e09c67e98b2a9c0e4ad
Tx public key: 54ed42af6c56a6eeba2b351555146de946dfb41faad5256c33d304e4ac224d81
Timestamp: 1577861903 Timestamp [UCT]: 2020-01-01 06:58:23 Age [y:d:h:m:s]: 05:113:11:42:18
Block: 36188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1230991 RingCT/type: yes/0
Extra: 0154ed42af6c56a6eeba2b351555146de946dfb41faad5256c33d304e4ac224d8102110000001ad81c26c0000000000000000000

1 output(s) for total of 465.695975480000 dcy

stealth address amount amount idx
00: 4ab525ec57ce9ee5382a041165be8574f49faeab444a52711e426bcfedfa8ce4 465.695975480000 61224 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 36198, "vin": [ { "gen": { "height": 36188 } } ], "vout": [ { "amount": 465695975480, "target": { "key": "4ab525ec57ce9ee5382a041165be8574f49faeab444a52711e426bcfedfa8ce4" } } ], "extra": [ 1, 84, 237, 66, 175, 108, 86, 166, 238, 186, 43, 53, 21, 85, 20, 109, 233, 70, 223, 180, 31, 170, 213, 37, 108, 51, 211, 4, 228, 172, 34, 77, 129, 2, 17, 0, 0, 0, 26, 216, 28, 38, 192, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8