Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c09e02f4c679e4e5537a39611466ba5f86c9b8e59738ee73486e7ec30aea1e

Tx prefix hash: e4f4a2d663444cd4a3cf14b948458ec7e0a3a4638621b2d16651dac9c6a3968f
Tx public key: 0cc512c0e2fac6053315f2c22ecd96441d30c99391056ce7184ea2f38cf1c00d
Timestamp: 1737898517 Timestamp [UCT]: 2025-01-26 13:35:17 Age [y:d:h:m:s]: 00:142:11:21:14
Block: 1205745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101558 RingCT/type: yes/0
Extra: 010cc512c0e2fac6053315f2c22ecd96441d30c99391056ce7184ea2f38cf1c00d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ee302e1f7f86b66e3dada53ecd5a468178df24f196ebf6322eeabf19558a5ed 0.600000000000 1692444 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": 1205755, "vin": [ { "gen": { "height": 1205745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ee302e1f7f86b66e3dada53ecd5a468178df24f196ebf6322eeabf19558a5ed" } } ], "extra": [ 1, 12, 197, 18, 192, 226, 250, 198, 5, 51, 21, 242, 194, 46, 205, 150, 68, 29, 48, 201, 147, 145, 5, 108, 231, 24, 78, 162, 243, 140, 241, 192, 13, 2, 17, 0, 0, 0, 5, 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