Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5869b292702c8e5176012aa3db71f3262c3b26ff434e9c03b5a18d6b11e7c201

Tx prefix hash: 9b5696fdb00b0dc56843a39b8d98df1e6833c2ee716068b7f72c81c8bc0c57e8
Tx public key: 18784458e8da491ddeb979dbe47d40c567af1ae58c58d706ee9ef341ea059732
Timestamp: 1736572504 Timestamp [UCT]: 2025-01-11 05:15:04 Age [y:d:h:m:s]: 00:164:23:45:18
Block: 1194808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117499 RingCT/type: yes/0
Extra: 0118784458e8da491ddeb979dbe47d40c567af1ae58c58d706ee9ef341ea059732021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76a3c8fe97a4257ffb5c6f53b35d2b51831dab924e3ce11a0bfd3da37cd4d3c7 0.600000000000 1681385 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": 1194818, "vin": [ { "gen": { "height": 1194808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76a3c8fe97a4257ffb5c6f53b35d2b51831dab924e3ce11a0bfd3da37cd4d3c7" } } ], "extra": [ 1, 24, 120, 68, 88, 232, 218, 73, 29, 222, 185, 121, 219, 228, 125, 64, 197, 103, 175, 26, 229, 140, 88, 215, 6, 238, 158, 243, 65, 234, 5, 151, 50, 2, 17, 0, 0, 0, 2, 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