Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d05727a80ca3cd74f190b025a94411b397fb09648fe8abc2c7ad70af82c25a

Tx prefix hash: bd18577810e8b0b89fe6269f9d1b067291081246a957f7d54fc36b258c20f7fb
Tx public key: ee9702d8c0446ec437c289abaf2ec8066280281615eb3ff989ef75bc6fd024dc
Timestamp: 1584525383 Timestamp [UCT]: 2020-03-18 09:56:23 Age [y:d:h:m:s]: 04:291:08:05:07
Block: 84884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103868 RingCT/type: yes/0
Extra: 01ee9702d8c0446ec437c289abaf2ec8066280281615eb3ff989ef75bc6fd024dc0211000000048a2ee0d9000000000000000000

1 output(s) for total of 321.177308070000 dcy

stealth address amount amount idx
00: 1f2b61a8943272a42c18dd7c73194e179194e0345e7f8041cf7ad604bacc2c69 321.177308070000 153652 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": 84894, "vin": [ { "gen": { "height": 84884 } } ], "vout": [ { "amount": 321177308070, "target": { "key": "1f2b61a8943272a42c18dd7c73194e179194e0345e7f8041cf7ad604bacc2c69" } } ], "extra": [ 1, 238, 151, 2, 216, 192, 68, 110, 196, 55, 194, 137, 171, 175, 46, 200, 6, 98, 128, 40, 22, 21, 235, 63, 249, 137, 239, 117, 188, 111, 208, 36, 220, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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