Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ac149c18b96ab0fcdc495867c74c1877003e17ef548e62b9f414a9dc4b8b2fe

Tx prefix hash: 144f59b8a4c04ad80ab7038bdbd7156888e59403b3474d23d1965b882b86b8e2
Tx public key: ddf8dbd2dda3643b1b6dc7fa640a74b4985d2b7f80fce9daadb9475ab8401ef4
Timestamp: 1699489097 Timestamp [UCT]: 2023-11-09 00:18:17 Age [y:d:h:m:s]: 01:357:02:47:48
Block: 887519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514134 RingCT/type: yes/0
Extra: 01ddf8dbd2dda3643b1b6dc7fa640a74b4985d2b7f80fce9daadb9475ab8401ef40211000000024b8f5122000000000000000000

1 output(s) for total of 0.703527581000 dcy

stealth address amount amount idx
00: 427bd2ed740ac14225085903f9a318cbc59725ae99bd4711e3110da17b0d37e5 0.703527581000 1343404 of 0

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": 887529, "vin": [ { "gen": { "height": 887519 } } ], "vout": [ { "amount": 703527581, "target": { "key": "427bd2ed740ac14225085903f9a318cbc59725ae99bd4711e3110da17b0d37e5" } } ], "extra": [ 1, 221, 248, 219, 210, 221, 163, 100, 59, 27, 109, 199, 250, 100, 10, 116, 180, 152, 93, 43, 127, 128, 252, 233, 218, 173, 185, 71, 90, 184, 64, 30, 244, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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