Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 686dea0f147064059cd2de3e71dc493d1e6d1a515df57df2080b75d1407af791

Tx prefix hash: 0278f0e8aa1912547e0c4740da86f54abbe41d28d69b9792bdf3d56cd97fd4f4
Tx public key: bf2dbf32ce70fda99296d781b5bcc5937dda974012d3396912624252b94ca4ef
Timestamp: 1707519759 Timestamp [UCT]: 2024-02-09 23:02:39 Age [y:d:h:m:s]: 01:130:01:25:18
Block: 954074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353934 RingCT/type: yes/0
Extra: 01bf2dbf32ce70fda99296d781b5bcc5937dda974012d3396912624252b94ca4ef02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a11f84596762c6d9abe6e6f17e0c9322ffa1f09201bfe0e12f15e59b1b00fb6f 0.600000000000 1413346 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": 954084, "vin": [ { "gen": { "height": 954074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a11f84596762c6d9abe6e6f17e0c9322ffa1f09201bfe0e12f15e59b1b00fb6f" } } ], "extra": [ 1, 191, 45, 191, 50, 206, 112, 253, 169, 146, 150, 215, 129, 181, 188, 197, 147, 125, 218, 151, 64, 18, 211, 57, 105, 18, 98, 66, 82, 185, 76, 164, 239, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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