Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a0046699360682e7cf1386803f98d60f57ec9fd3a3a3686adacd6e10cda346a

Tx prefix hash: 95d61319247b2c1a04bb8ffb9da65bc0dee1fc33f99cb33d43c82f0cfded76aa
Tx public key: db5a409414e9489d1c6149b6a3fd0e9d67534b8e53e79fe689cb869782c954f2
Timestamp: 1705018697 Timestamp [UCT]: 2024-01-12 00:18:17 Age [y:d:h:m:s]: 01:305:11:04:35
Block: 933339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477141 RingCT/type: yes/0
Extra: 01db5a409414e9489d1c6149b6a3fd0e9d67534b8e53e79fe689cb869782c954f2021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f1ed6508c9e10afd0da69112fd768dfbca7421ed0a8806b30a34abe13d526a9 0.600000000000 1391301 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": 933349, "vin": [ { "gen": { "height": 933339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f1ed6508c9e10afd0da69112fd768dfbca7421ed0a8806b30a34abe13d526a9" } } ], "extra": [ 1, 219, 90, 64, 148, 20, 233, 72, 157, 28, 97, 73, 182, 163, 253, 14, 157, 103, 83, 75, 142, 83, 231, 159, 230, 137, 203, 134, 151, 130, 201, 84, 242, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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