Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90fd0fa187399c02d9f1c2a1e84af79ffaaf1c5aaffd9415280327f86b48db21

Tx prefix hash: 8a52473c8738268b845d44b21e0cffda66dce1764cc66dbd0a9eb1f615062b9d
Tx public key: a74ca8a34f7448e20d18c32636d8cd0b1df2cb3f80d7e6389ee85bd4fe7450d6
Timestamp: 1633150805 Timestamp [UCT]: 2021-10-02 05:00:05 Age [y:d:h:m:s]: 04:030:13:44:50
Block: 344949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1057167 RingCT/type: yes/0
Extra: 01a74ca8a34f7448e20d18c32636d8cd0b1df2cb3f80d7e6389ee85bd4fe7450d6021100000001fdc024ec000000000000000000

1 output(s) for total of 44.162003484000 dcy

stealth address amount amount idx
00: 03095aa97d72000331e94b3fba569e3f61d2c9f977c5c4105f66e4abbaf54106 44.162003484000 707649 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": 344959, "vin": [ { "gen": { "height": 344949 } } ], "vout": [ { "amount": 44162003484, "target": { "key": "03095aa97d72000331e94b3fba569e3f61d2c9f977c5c4105f66e4abbaf54106" } } ], "extra": [ 1, 167, 76, 168, 163, 79, 116, 72, 226, 13, 24, 195, 38, 54, 216, 205, 11, 29, 242, 203, 63, 128, 215, 230, 56, 158, 232, 91, 212, 254, 116, 80, 214, 2, 17, 0, 0, 0, 1, 253, 192, 36, 236, 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