Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4904471349cca3aa77d0b0db6d641cfb41af2a830d7b15ab90759d5371769aa

Tx prefix hash: 4c67aa808496d5b4131b54853afbd76cb27d1088ccb84817036dbd2ea489fd4e
Tx public key: e93c85f6fb0a42c772ae2ac703f8f5b3aa6e74c5ad381b132856e4063ddcebbe
Timestamp: 1723073184 Timestamp [UCT]: 2024-08-07 23:26:24 Age [y:d:h:m:s]: 00:316:06:53:14
Block: 1083034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225845 RingCT/type: yes/0
Extra: 01e93c85f6fb0a42c772ae2ac703f8f5b3aa6e74c5ad381b132856e4063ddcebbe021100000001341001ae000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08468612336fe9c38a605ba44fc5e870c708d0db9bfec00197b0d69412c70411 0.600000000000 1556869 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": 1083044, "vin": [ { "gen": { "height": 1083034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08468612336fe9c38a605ba44fc5e870c708d0db9bfec00197b0d69412c70411" } } ], "extra": [ 1, 233, 60, 133, 246, 251, 10, 66, 199, 114, 174, 42, 199, 3, 248, 245, 179, 170, 110, 116, 197, 173, 56, 27, 19, 40, 86, 228, 6, 61, 220, 235, 190, 2, 17, 0, 0, 0, 1, 52, 16, 1, 174, 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