Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4db18c8accd9119548dbfbf7bab6dbdb5b058c99184b844410b8a9d81f2cd43f

Tx prefix hash: cb50f1f05615eccd449ca49fc883a622d1989968d3ad4b763378be12a441f61c
Tx public key: b9b90ce769e13ef84fb5cbf433aaff3e262a359a17fd27cdf75f3f8619fca047
Timestamp: 1727581695 Timestamp [UCT]: 2024-09-29 03:48:15 Age [y:d:h:m:s]: 00:056:10:22:02
Block: 1120421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40317 RingCT/type: yes/0
Extra: 01b9b90ce769e13ef84fb5cbf433aaff3e262a359a17fd27cdf75f3f8619fca047021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e82b6c4cdb12828de4c5e029d66500974e2e7490fb950674304e71a54ec024a9 0.600000000000 1602328 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": 1120431, "vin": [ { "gen": { "height": 1120421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e82b6c4cdb12828de4c5e029d66500974e2e7490fb950674304e71a54ec024a9" } } ], "extra": [ 1, 185, 185, 12, 231, 105, 225, 62, 248, 79, 181, 203, 244, 51, 170, 255, 62, 38, 42, 53, 154, 23, 253, 39, 205, 247, 95, 63, 134, 25, 252, 160, 71, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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