Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3788e6db814e36a96837fc0510aae4e723c0ed4ff137606bac4a490995210ab

Tx prefix hash: df5b6c019f8963bd391ab6ce0a8060cd72744aa7e4b065119b4a1f423264f82f
Tx public key: 067e1019b82cd75e79cf8c85f35287aed89c67599b3e2f1612ae1832e3b17b80
Timestamp: 1723160460 Timestamp [UCT]: 2024-08-08 23:41:00 Age [y:d:h:m:s]: 00:287:08:59:58
Block: 1083749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205324 RingCT/type: yes/0
Extra: 01067e1019b82cd75e79cf8c85f35287aed89c67599b3e2f1612ae1832e3b17b80021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7abb72743150a3df234404f2ef432426d72a539f0e9540c08c43dd11fa0e8eca 0.600000000000 1557784 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": 1083759, "vin": [ { "gen": { "height": 1083749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7abb72743150a3df234404f2ef432426d72a539f0e9540c08c43dd11fa0e8eca" } } ], "extra": [ 1, 6, 126, 16, 25, 184, 44, 215, 94, 121, 207, 140, 133, 243, 82, 135, 174, 216, 156, 103, 89, 155, 62, 47, 22, 18, 174, 24, 50, 227, 177, 123, 128, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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