Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41d87f6ab194c00c764993ccab27b72db2442af261227964c3ebb694b1ae1078

Tx prefix hash: 2436b9622d1c3ed817d15ad84bba03366f342cdef27d5424cd1fb6ceee231f75
Tx public key: 48e85a3884b20c7067d5efa415253c2d3fcdd5b63b0bf92890d413e4c2fd31dc
Timestamp: 1712492344 Timestamp [UCT]: 2024-04-07 12:19:04 Age [y:d:h:m:s]: 01:003:11:54:42
Block: 995286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263478 RingCT/type: yes/0
Extra: 0148e85a3884b20c7067d5efa415253c2d3fcdd5b63b0bf92890d413e4c2fd31dc0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa7144420f03b879f3c77022e56ed5940079e405ba09e88df23132277158a41a 0.600000000000 1455692 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": 995296, "vin": [ { "gen": { "height": 995286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa7144420f03b879f3c77022e56ed5940079e405ba09e88df23132277158a41a" } } ], "extra": [ 1, 72, 232, 90, 56, 132, 178, 12, 112, 103, 213, 239, 164, 21, 37, 60, 45, 63, 205, 213, 182, 59, 11, 249, 40, 144, 212, 19, 228, 194, 253, 49, 220, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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