Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0bd38ad20dd92fab33231d7c1db88d578cb77ad7cd15a7d9b2848711253871

Tx prefix hash: 377ed5852b74a499a71c06e31ab08b2b268db784cac58764782da5f50c919733
Tx public key: f9d6fad3cbb27e79ba4a37f59094bd4dc0e4a5baebd67df56f5285dbce346245
Timestamp: 1582434955 Timestamp [UCT]: 2020-02-23 05:15:55 Age [y:d:h:m:s]: 05:115:13:49:04
Block: 70621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1235805 RingCT/type: yes/0
Extra: 01f9d6fad3cbb27e79ba4a37f59094bd4dc0e4a5baebd67df56f5285dbce346245021100000002724f989b000000000000000000

1 output(s) for total of 358.099828976000 dcy

stealth address amount amount idx
00: e64bf4d967cbb9218022d95e2936477d890f0f230ce104c9b0c09a09e3e436db 358.099828976000 130495 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": 70631, "vin": [ { "gen": { "height": 70621 } } ], "vout": [ { "amount": 358099828976, "target": { "key": "e64bf4d967cbb9218022d95e2936477d890f0f230ce104c9b0c09a09e3e436db" } } ], "extra": [ 1, 249, 214, 250, 211, 203, 178, 126, 121, 186, 74, 55, 245, 144, 148, 189, 77, 192, 228, 165, 186, 235, 214, 125, 245, 111, 82, 133, 219, 206, 52, 98, 69, 2, 17, 0, 0, 0, 2, 114, 79, 152, 155, 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