Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dd56ae8a9f830071534855375c060a86ad3c57b6c9b6ee70f36111bc59a0d7f

Tx prefix hash: fa0001937d60693aa3385f828b77edc63daad34080ee602c717cabcab221bbe2
Tx public key: a5a4a992985245df5d76f6c972f733a5f96af67eaf4410e8876aa02a67fdb6a6
Timestamp: 1704503257 Timestamp [UCT]: 2024-01-06 01:07:37 Age [y:d:h:m:s]: 01:005:03:29:39
Block: 929052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265017 RingCT/type: yes/0
Extra: 01a5a4a992985245df5d76f6c972f733a5f96af67eaf4410e8876aa02a67fdb6a60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bf63a1fe2f349172f8ad3046185794bfc68376b0580a19d5724d04d41220a46 0.600000000000 1386920 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": 929062, "vin": [ { "gen": { "height": 929052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bf63a1fe2f349172f8ad3046185794bfc68376b0580a19d5724d04d41220a46" } } ], "extra": [ 1, 165, 164, 169, 146, 152, 82, 69, 223, 93, 118, 246, 201, 114, 247, 51, 165, 249, 106, 246, 126, 175, 68, 16, 232, 135, 106, 160, 42, 103, 253, 182, 166, 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