Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0c94651c9aa5e498e5ecca989e381006424c77d4393c0403c92e7f99180205

Tx prefix hash: 683f2d336163cbcabe61056c9b1a379c6741be2713d76b1343c0989cafd7fe2a
Tx public key: 07cc4e9bbf9c38414821b507e112b7cb8766b1a43ea44a06977af82d6a583987
Timestamp: 1727069235 Timestamp [UCT]: 2024-09-23 05:27:15 Age [y:d:h:m:s]: 00:194:04:33:22
Block: 1116161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138603 RingCT/type: yes/0
Extra: 0107cc4e9bbf9c38414821b507e112b7cb8766b1a43ea44a06977af82d6a583987021100000019e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c31e043624f2417b524e0985fb8378c39e9b570930ea11fdfb11bb7c84c4b87 0.600000000000 1596548 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": 1116171, "vin": [ { "gen": { "height": 1116161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c31e043624f2417b524e0985fb8378c39e9b570930ea11fdfb11bb7c84c4b87" } } ], "extra": [ 1, 7, 204, 78, 155, 191, 156, 56, 65, 72, 33, 181, 7, 225, 18, 183, 203, 135, 102, 177, 164, 62, 164, 74, 6, 151, 122, 248, 45, 106, 88, 57, 135, 2, 17, 0, 0, 0, 25, 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