Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6676be344449909ed07ef98297184f5e0bfd7b5824ef3f5d4f20e93415af424d

Tx prefix hash: d76a3d170149a74ad90788805d257838ce6a53d5ac23975e0436bf3f935bafe5
Tx public key: 4a0906052b8d8f51227f370a882a534d3fa4b2a33998f08670c4781006d83b83
Timestamp: 1712082752 Timestamp [UCT]: 2024-04-02 18:32:32 Age [y:d:h:m:s]: 00:222:15:28:52
Block: 991887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159410 RingCT/type: yes/0
Extra: 014a0906052b8d8f51227f370a882a534d3fa4b2a33998f08670c4781006d83b8302110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c71a60e158c48ea7b5b81d73ac02c90d1e3089275e93a36b3f7e1b7904f31e04 0.600000000000 1452223 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": 991897, "vin": [ { "gen": { "height": 991887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c71a60e158c48ea7b5b81d73ac02c90d1e3089275e93a36b3f7e1b7904f31e04" } } ], "extra": [ 1, 74, 9, 6, 5, 43, 141, 143, 81, 34, 127, 55, 10, 136, 42, 83, 77, 63, 164, 178, 163, 57, 152, 240, 134, 112, 196, 120, 16, 6, 216, 59, 131, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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