Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ebf9472614f26fa3c7066edea18deeafbe6d83897c8f7c3e63729fb4673d852

Tx prefix hash: 3b96868a68a8cc32b7e3de5a9708bc6561d4d4784c6cc8f00cee0d60ef0d2473
Tx public key: 7a2ce03be322207db2c8eb8d69ef7558cabcaffff33be575abeb948d024dffdb
Timestamp: 1737043610 Timestamp [UCT]: 2025-01-16 16:06:50 Age [y:d:h:m:s]: 00:151:22:43:23
Block: 1198705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108307 RingCT/type: yes/0
Extra: 017a2ce03be322207db2c8eb8d69ef7558cabcaffff33be575abeb948d024dffdb0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de7e9a2dfe9a1b67046a229954a068f2e36c62f04b56ce3d1022548e416e1333 0.600000000000 1685332 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": 1198715, "vin": [ { "gen": { "height": 1198705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de7e9a2dfe9a1b67046a229954a068f2e36c62f04b56ce3d1022548e416e1333" } } ], "extra": [ 1, 122, 44, 224, 59, 227, 34, 32, 125, 178, 200, 235, 141, 105, 239, 117, 88, 202, 188, 175, 255, 243, 59, 229, 117, 171, 235, 148, 141, 2, 77, 255, 219, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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