Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36eb4d4201f5de75b35543a14f0a2c4578c2fe64ecd31351e533f51a3264f071

Tx prefix hash: f738ed586a312d3656c1cd59e5562a0f6989dfae699afbab4f2db9a5accb1bb3
Tx public key: 5fbad0be40669f40c9d4cfced5986c2e966d391bea286130d39f71b0f895d1b7
Timestamp: 1719315601 Timestamp [UCT]: 2024-06-25 11:40:01 Age [y:d:h:m:s]: 01:134:23:22:34
Block: 1051874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355011 RingCT/type: yes/0
Extra: 015fbad0be40669f40c9d4cfced5986c2e966d391bea286130d39f71b0f895d1b70211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7aa23d351d3170f2151be052b56486cdf9d07f4b84e6a0f875d517a18f429670 0.600000000000 1522193 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": 1051884, "vin": [ { "gen": { "height": 1051874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aa23d351d3170f2151be052b56486cdf9d07f4b84e6a0f875d517a18f429670" } } ], "extra": [ 1, 95, 186, 208, 190, 64, 102, 159, 64, 201, 212, 207, 206, 213, 152, 108, 46, 150, 109, 57, 27, 234, 40, 97, 48, 211, 159, 113, 176, 248, 149, 209, 183, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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