Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d41b60afc606a7d1369837f2e2a022cce6c6e7b4fcec80925a0c8c52347fb84

Tx prefix hash: 52f297ce8472ff8bae5f4475f214780754495c188be57180ee2520e8b6b8cb7c
Tx public key: 591929e5c9272f1c633a29b40393bf8e8e8a7cf340c8b7f6982407a8d7962b84
Timestamp: 1731626064 Timestamp [UCT]: 2024-11-14 23:14:24 Age [y:d:h:m:s]: 00:165:04:11:44
Block: 1153849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117892 RingCT/type: yes/0
Extra: 01591929e5c9272f1c633a29b40393bf8e8e8a7cf340c8b7f6982407a8d7962b84021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75afff1defa4355990afa7214b36da4497104e02a07e5c1b8949333ee19b8f7f 0.600000000000 1639460 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": 1153859, "vin": [ { "gen": { "height": 1153849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75afff1defa4355990afa7214b36da4497104e02a07e5c1b8949333ee19b8f7f" } } ], "extra": [ 1, 89, 25, 41, 229, 201, 39, 47, 28, 99, 58, 41, 180, 3, 147, 191, 142, 142, 138, 124, 243, 64, 200, 183, 246, 152, 36, 7, 168, 215, 150, 43, 132, 2, 17, 0, 0, 0, 3, 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