Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64f70a9d25d6f5ebb907ea242458d50339ed8f9b3bcc1f3f459719ba845db61c

Tx prefix hash: e8ff3bd8222d6c42eaac9959f00720685b9d6a71e9c7cffee7b15eb0e4be3fe8
Tx public key: 03aa41603458764205f545313cacaf59b800a1dfa58fdc810de26273ca136fe8
Timestamp: 1702689093 Timestamp [UCT]: 2023-12-16 01:11:33 Age [y:d:h:m:s]: 01:128:14:46:24
Block: 914039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353063 RingCT/type: yes/0
Extra: 0103aa41603458764205f545313cacaf59b800a1dfa58fdc810de26273ca136fe8021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59e511d49f82964a2c1957d84e87b1184f156c743fff92f2dd859819c1e35c45 0.600000000000 1371321 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": 914049, "vin": [ { "gen": { "height": 914039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59e511d49f82964a2c1957d84e87b1184f156c743fff92f2dd859819c1e35c45" } } ], "extra": [ 1, 3, 170, 65, 96, 52, 88, 118, 66, 5, 245, 69, 49, 60, 172, 175, 89, 184, 0, 161, 223, 165, 143, 220, 129, 13, 226, 98, 115, 202, 19, 111, 232, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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