Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 266ee45dc09531e795aa0c9b2e4cea67787568c37296dd70a7e1ea79a9635ae9

Tx prefix hash: 89c26ef1757d20d83d17b382ff84269d37b01bb659cc5f3f3e17d3032cc76a7a
Tx public key: 041d5f0115f934eb90ef8255bfe8986c32cab6b74127d3a28da596f545443c71
Timestamp: 1731787848 Timestamp [UCT]: 2024-11-16 20:10:48 Age [y:d:h:m:s]: 00:214:03:40:25
Block: 1155177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152799 RingCT/type: yes/0
Extra: 01041d5f0115f934eb90ef8255bfe8986c32cab6b74127d3a28da596f545443c71021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a42fad0b895ea5639e4d0643aa13a0bab7ad4100fc8cd2f6ef99880af7f082e 0.600000000000 1640792 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": 1155187, "vin": [ { "gen": { "height": 1155177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a42fad0b895ea5639e4d0643aa13a0bab7ad4100fc8cd2f6ef99880af7f082e" } } ], "extra": [ 1, 4, 29, 95, 1, 21, 249, 52, 235, 144, 239, 130, 85, 191, 232, 152, 108, 50, 202, 182, 183, 65, 39, 211, 162, 141, 165, 150, 245, 69, 68, 60, 113, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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