Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a282ba29404b2af45cbeb59a56dc267a8168da7dc03e229c892cda89a4739c9

Tx prefix hash: 800b3054938780bec12da929d91b35c1b8d3f85b9fc3a4ebce90bf7f97ed2b6e
Tx public key: be8d53f0c2bb5f4c9074767915a2de0026898460e717e2e2cd51f2293a595fa5
Timestamp: 1723317281 Timestamp [UCT]: 2024-08-10 19:14:41 Age [y:d:h:m:s]: 01:117:18:01:12
Block: 1085059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342657 RingCT/type: yes/0
Extra: 01be8d53f0c2bb5f4c9074767915a2de0026898460e717e2e2cd51f2293a595fa502110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54799250fbde017f2d93d8a67498e5773f0ff0f3750f6764728bca757e971661 0.600000000000 1559552 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": 1085069, "vin": [ { "gen": { "height": 1085059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54799250fbde017f2d93d8a67498e5773f0ff0f3750f6764728bca757e971661" } } ], "extra": [ 1, 190, 141, 83, 240, 194, 187, 95, 76, 144, 116, 118, 121, 21, 162, 222, 0, 38, 137, 132, 96, 231, 23, 226, 226, 205, 81, 242, 41, 58, 89, 95, 165, 2, 17, 0, 0, 0, 11, 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