Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e60bd01162dcb15e73e5114f5f7f5b74cdd50bb098d77294aa5f664d0fb449a

Tx prefix hash: b3f61894e4dd322874e66117b858749e1657af83fc16fbfabbba0205aa96001f
Tx public key: f3f43cf41a77f22249dadc9be352acddec744d2e4f4b2a8fdc44fc1d2e9b2015
Timestamp: 1676294237 Timestamp [UCT]: 2023-02-13 13:17:17 Age [y:d:h:m:s]: 02:102:07:54:49
Block: 696109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594760 RingCT/type: yes/0
Extra: 01f3f43cf41a77f22249dadc9be352acddec744d2e4f4b2a8fdc44fc1d2e9b20150211000000045029cbac000000000000000000

1 output(s) for total of 3.030413091000 dcy

stealth address amount amount idx
00: e739d83ee5049fd9145e622d7c0779d8078f0da09d507e59219a7a5395e3c131 3.030413091000 1139074 of 0

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": 696119, "vin": [ { "gen": { "height": 696109 } } ], "vout": [ { "amount": 3030413091, "target": { "key": "e739d83ee5049fd9145e622d7c0779d8078f0da09d507e59219a7a5395e3c131" } } ], "extra": [ 1, 243, 244, 60, 244, 26, 119, 242, 34, 73, 218, 220, 155, 227, 82, 172, 221, 236, 116, 77, 46, 79, 75, 42, 143, 220, 68, 252, 29, 46, 155, 32, 21, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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