Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40928324c5eab89b18ca230b55a3778cd077444d3d6e160cb727daa2dbc37a39

Tx prefix hash: 70713174325f71b7019fd0654a16d3c504d2758522ebe39de39578845e0fddcb
Tx public key: 4a794ff74bdcc538869f5d76146ce9e0b402b53435f7abee4e7e7f991eadc85d
Timestamp: 1723218183 Timestamp [UCT]: 2024-08-09 15:43:03 Age [y:d:h:m:s]: 00:233:19:24:39
Block: 1084229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166994 RingCT/type: yes/0
Extra: 014a794ff74bdcc538869f5d76146ce9e0b402b53435f7abee4e7e7f991eadc85d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e0537a17dbce61e1bff6e42a0c4a793b2c6764948d39e143f7a86d53786ed07 0.600000000000 1558430 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": 1084239, "vin": [ { "gen": { "height": 1084229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e0537a17dbce61e1bff6e42a0c4a793b2c6764948d39e143f7a86d53786ed07" } } ], "extra": [ 1, 74, 121, 79, 247, 75, 220, 197, 56, 134, 159, 93, 118, 20, 108, 233, 224, 180, 2, 181, 52, 53, 247, 171, 238, 78, 126, 127, 153, 30, 173, 200, 93, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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