Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe50b59c81908328b1ce86fb687697b18cac3cd237be39ea5b288cfc47d8f3f5

Tx prefix hash: ab667a187cb8a2f27ce86a37b96f5ea493fc5fd8f1ca89dff5cc13ed4f93776b
Tx public key: 9ea353414dde75d166eb7352f97d1587f1d3b2912fac302c3eec2824f7cb82a8
Timestamp: 1734520700 Timestamp [UCT]: 2024-12-18 11:18:20 Age [y:d:h:m:s]: 00:109:23:31:10
Block: 1177857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78353 RingCT/type: yes/0
Extra: 019ea353414dde75d166eb7352f97d1587f1d3b2912fac302c3eec2824f7cb82a8021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90c074aa8866595d12477383d05d5ff8b4f44bbc495d034a164f2376336f4697 0.600000000000 1664236 of 15

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": 1177867, "vin": [ { "gen": { "height": 1177857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90c074aa8866595d12477383d05d5ff8b4f44bbc495d034a164f2376336f4697" } } ], "extra": [ 1, 158, 163, 83, 65, 77, 222, 117, 209, 102, 235, 115, 82, 249, 125, 21, 135, 241, 211, 178, 145, 47, 172, 48, 44, 62, 236, 40, 36, 247, 203, 130, 168, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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