Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18c0e674c538649e408de575f848f0a7061e1d17f4bda0799e8130565d9a220c

Tx prefix hash: 535f55df8153d766d958aa7d28da7da24210673be6ac9fc8f8732bf534b14906
Tx public key: 67da2013b7f3a8d4147055164f83d243aa2ea5dd72f38e1178d9c1b717eb764f
Timestamp: 1713470165 Timestamp [UCT]: 2024-04-18 19:56:05 Age [y:d:h:m:s]: 00:363:12:02:29
Block: 1003409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259874 RingCT/type: yes/0
Extra: 0167da2013b7f3a8d4147055164f83d243aa2ea5dd72f38e1178d9c1b717eb764f021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 275c23eda12e5df3e435879b94a2eccd1f97d1d5c427336bd4721d1f36e1773d 0.600000000000 1463939 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": 1003419, "vin": [ { "gen": { "height": 1003409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "275c23eda12e5df3e435879b94a2eccd1f97d1d5c427336bd4721d1f36e1773d" } } ], "extra": [ 1, 103, 218, 32, 19, 183, 243, 168, 212, 20, 112, 85, 22, 79, 131, 210, 67, 170, 46, 165, 221, 114, 243, 142, 17, 120, 217, 193, 183, 23, 235, 118, 79, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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