Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ed4638850c187941c470ad9655e9414c96a0b278baa943a335d643b67ea0167

Tx prefix hash: 9052aee4ce6aa220f77958a2c01f6d451490eb088f1a765690aa0b4cdcacfca7
Tx public key: 08b8f8414f1cc38ca74b115422a46ba6eebf4d89f5dec87c898f0fbf7040bcf2
Timestamp: 1704502102 Timestamp [UCT]: 2024-01-06 00:48:22 Age [y:d:h:m:s]: 01:085:01:59:00
Block: 929043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321925 RingCT/type: yes/0
Extra: 0108b8f8414f1cc38ca74b115422a46ba6eebf4d89f5dec87c898f0fbf7040bcf20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 338f749e3b0e2f22c7e2577aee842cdf5c57105caa9876b9781991ee7e963a9d 0.600000000000 1386911 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": 929053, "vin": [ { "gen": { "height": 929043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "338f749e3b0e2f22c7e2577aee842cdf5c57105caa9876b9781991ee7e963a9d" } } ], "extra": [ 1, 8, 184, 248, 65, 79, 28, 195, 140, 167, 75, 17, 84, 34, 164, 107, 166, 238, 191, 77, 137, 245, 222, 200, 124, 137, 143, 15, 191, 112, 64, 188, 242, 2, 17, 0, 0, 0, 1, 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