Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 578467167f2d742c5f005fd5fa629a7fe5eb36e4f232b1091d8fe1c028772a24

Tx prefix hash: 1891299cb5f2b7c1bc66f2047ffefb331c31c817e7ea06b45023e04f7c006376
Tx public key: 9d74d32be0e45765cd38203cd1470627a91917a395ea1b05778729c3ec701124
Timestamp: 1732524012 Timestamp [UCT]: 2024-11-25 08:40:12 Age [y:d:h:m:s]: 00:353:23:06:02
Block: 1161285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250525 RingCT/type: yes/0
Extra: 019d74d32be0e45765cd38203cd1470627a91917a395ea1b05778729c3ec7011240211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7d6d7dbf82f13ec59e3e75f3c980f41911f3481b6de4473f0e7b0cbf826b290 0.600000000000 1646936 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": 1161295, "vin": [ { "gen": { "height": 1161285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7d6d7dbf82f13ec59e3e75f3c980f41911f3481b6de4473f0e7b0cbf826b290" } } ], "extra": [ 1, 157, 116, 211, 43, 224, 228, 87, 101, 205, 56, 32, 60, 209, 71, 6, 39, 169, 25, 23, 163, 149, 234, 27, 5, 119, 135, 41, 195, 236, 112, 17, 36, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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