Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b5ab75abc2fe3098c93f68ef2dbbbdca3e15710e79378407f6ff57733f021c6

Tx prefix hash: c668d94065054d593295c2542cdb6795adc0fa589906a1c1ade14362d7339652
Tx public key: 050dee06857c5d1209437a8c132455d9a521c9b0be4c98792836a5ae7c25c270
Timestamp: 1738211924 Timestamp [UCT]: 2025-01-30 04:38:44 Age [y:d:h:m:s]: 00:141:14:57:28
Block: 1208120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101130 RingCT/type: yes/0
Extra: 01050dee06857c5d1209437a8c132455d9a521c9b0be4c98792836a5ae7c25c2700211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d43e41b0c142908d6c7a7a1996deffeadf6ac7c02d0ec41170bfe9b728eaf3e 0.600000000000 1694849 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": 1208130, "vin": [ { "gen": { "height": 1208120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d43e41b0c142908d6c7a7a1996deffeadf6ac7c02d0ec41170bfe9b728eaf3e" } } ], "extra": [ 1, 5, 13, 238, 6, 133, 124, 93, 18, 9, 67, 122, 140, 19, 36, 85, 217, 165, 33, 201, 176, 190, 76, 152, 121, 40, 54, 165, 174, 124, 37, 194, 112, 2, 17, 0, 0, 0, 7, 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