Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfbb46111fa012cb049d2b091c1e244afb2c307209c095d0a2df22bf6bfa2e33

Tx prefix hash: 6718753dc3e93b1f5055c85a8837fd0cece6f193d51a3226a3cbb25fefe50aeb
Tx public key: b4d3fb63b6bce7a0a401d4e88a72243342c01447ab77d5c8fda20133d7074afa
Timestamp: 1731985570 Timestamp [UCT]: 2024-11-19 03:06:10 Age [y:d:h:m:s]: 00:158:22:29:02
Block: 1156837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113413 RingCT/type: yes/0
Extra: 01b4d3fb63b6bce7a0a401d4e88a72243342c01447ab77d5c8fda20133d7074afa0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0489bb3bf2b0c0877d8c0ebf22df798741ff336df5cea27647fdc3e67446593d 0.600000000000 1642460 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": 1156847, "vin": [ { "gen": { "height": 1156837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0489bb3bf2b0c0877d8c0ebf22df798741ff336df5cea27647fdc3e67446593d" } } ], "extra": [ 1, 180, 211, 251, 99, 182, 188, 231, 160, 164, 1, 212, 232, 138, 114, 36, 51, 66, 192, 20, 71, 171, 119, 213, 200, 253, 162, 1, 51, 215, 7, 74, 250, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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