Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbce89191dfacfa02d80335d15b0750dbfb23731f46eb4cc133ed7fdb97a738d

Tx prefix hash: 9eecd862a70a94432e0f41f27afb82c8eeab8abab3161734a54793fef69cb25f
Tx public key: 1709c31a43c1a22144da0e8ec9cd0e9825c66981a81a6f8a48f1b2b8353fdf32
Timestamp: 1738327323 Timestamp [UCT]: 2025-01-31 12:42:03 Age [y:d:h:m:s]: 00:292:01:26:30
Block: 1209074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206496 RingCT/type: yes/0
Extra: 011709c31a43c1a22144da0e8ec9cd0e9825c66981a81a6f8a48f1b2b8353fdf320211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6945cbaafbf39f1a39b24360cc1a213439c3059063763b97eae73ab9115d5c47 0.600000000000 1695815 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": 1209084, "vin": [ { "gen": { "height": 1209074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6945cbaafbf39f1a39b24360cc1a213439c3059063763b97eae73ab9115d5c47" } } ], "extra": [ 1, 23, 9, 195, 26, 67, 193, 162, 33, 68, 218, 14, 142, 201, 205, 14, 152, 37, 198, 105, 129, 168, 26, 111, 138, 72, 241, 178, 184, 53, 63, 223, 50, 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