Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a0d9f7df560bb2939040aca4c1e426a6e408184641759d5f36b627a67f68c1c

Tx prefix hash: 77d045f54b68971600b7d124b40303362cd8d6726a00f32f49d01aba7eddd3b3
Tx public key: 1c1e64a447fb2af5269ac83fe5168ae96fccd68e39467b4d5715bde4d55611b0
Timestamp: 1736900753 Timestamp [UCT]: 2025-01-15 00:25:53 Age [y:d:h:m:s]: 00:154:14:57:40
Block: 1197522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110212 RingCT/type: yes/0
Extra: 011c1e64a447fb2af5269ac83fe5168ae96fccd68e39467b4d5715bde4d55611b0021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bf2f4c259fca261fb40649ae4b6cc0362f6d55179bb5820c9c26d2cd3f104a1 0.600000000000 1684131 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": 1197532, "vin": [ { "gen": { "height": 1197522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bf2f4c259fca261fb40649ae4b6cc0362f6d55179bb5820c9c26d2cd3f104a1" } } ], "extra": [ 1, 28, 30, 100, 164, 71, 251, 42, 245, 38, 154, 200, 63, 229, 22, 138, 233, 111, 204, 214, 142, 57, 70, 123, 77, 87, 21, 189, 228, 213, 86, 17, 176, 2, 17, 0, 0, 0, 7, 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