Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f466d6be662fe69e977422de7f90baad4d5b8edf6979f07a5ae0be73f76a095

Tx prefix hash: 23ea0b00056f9171009caec60e871839a854c35b6b48905707c4e3d78abc453d
Tx public key: c34017e13340d5e3005e68e9d149ccc08f1f3b1f3b22685c6569d09bf2d1a7e4
Timestamp: 1732513507 Timestamp [UCT]: 2024-11-25 05:45:07 Age [y:d:h:m:s]: 00:161:11:58:59
Block: 1161193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115271 RingCT/type: yes/0
Extra: 01c34017e13340d5e3005e68e9d149ccc08f1f3b1f3b22685c6569d09bf2d1a7e40211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d91e05664658f45e58826cc8611ed975ce6fd89df06a5020eb64c3da556ff686 0.600000000000 1646844 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": 1161203, "vin": [ { "gen": { "height": 1161193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d91e05664658f45e58826cc8611ed975ce6fd89df06a5020eb64c3da556ff686" } } ], "extra": [ 1, 195, 64, 23, 225, 51, 64, 213, 227, 0, 94, 104, 233, 209, 73, 204, 192, 143, 31, 59, 31, 59, 34, 104, 92, 101, 105, 208, 155, 242, 209, 167, 228, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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