Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df058ba47c1a2dccbdb80d55b44bec563cc056f61cee7b92fd354ed81cb55690

Tx prefix hash: 97156719adc25b2c0f1529d1bc3293904b0ee811344b5be3551278d3d4bc2a0f
Tx public key: 29accfc6856fe8590b3d8d8610ec4064cb2e8d6edde4f21484debe27050f45d0
Timestamp: 1706262879 Timestamp [UCT]: 2024-01-26 09:54:39 Age [y:d:h:m:s]: 01:030:08:47:19
Block: 943637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282760 RingCT/type: yes/0
Extra: 0129accfc6856fe8590b3d8d8610ec4064cb2e8d6edde4f21484debe27050f45d00211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56845cb30c23320f0df84194db6f8964dca19c3db11c663cb25d64e4064a2689 0.600000000000 1401845 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": 943647, "vin": [ { "gen": { "height": 943637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56845cb30c23320f0df84194db6f8964dca19c3db11c663cb25d64e4064a2689" } } ], "extra": [ 1, 41, 172, 207, 198, 133, 111, 232, 89, 11, 61, 141, 134, 16, 236, 64, 100, 203, 46, 141, 110, 221, 228, 242, 20, 132, 222, 190, 39, 5, 15, 69, 208, 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