Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a3dc10416f4099c350b62a6049daf5e17e4dcbfa0e741f112f3b88ad833291b

Tx prefix hash: e7560a261366d13691efc1acea614fe48a170ca54de7969a65fb5fb2326f3a40
Tx public key: 8f6aa3e7596a9a6976189b177db6b1af4ab64c2cb8d01aa999c625c862787c42
Timestamp: 1722852797 Timestamp [UCT]: 2024-08-05 10:13:17 Age [y:d:h:m:s]: 00:249:21:55:32
Block: 1081206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178513 RingCT/type: yes/0
Extra: 018f6aa3e7596a9a6976189b177db6b1af4ab64c2cb8d01aa999c625c862787c42021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f142c1c61cb0aa0fe5734d32dd87743dc9ef7e9dddee69f6d31ce9d257a60f2b 0.600000000000 1554861 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": 1081216, "vin": [ { "gen": { "height": 1081206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f142c1c61cb0aa0fe5734d32dd87743dc9ef7e9dddee69f6d31ce9d257a60f2b" } } ], "extra": [ 1, 143, 106, 163, 231, 89, 106, 154, 105, 118, 24, 155, 23, 125, 182, 177, 175, 74, 182, 76, 44, 184, 208, 26, 169, 153, 198, 37, 200, 98, 120, 124, 66, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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