Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8877084a42403e191c880bcacb6dbb8d72a4e76f26126cda39515cb839561a6

Tx prefix hash: 78e5b6d1d3388e4425d759526d1e93f008c6c7614b2bbea40d8b9dff5bfc8a9a
Tx public key: e968f3d179a36d9807a9aed7ba182367364197be90594d39b89a907fcb52d98e
Timestamp: 1706141227 Timestamp [UCT]: 2024-01-25 00:07:07 Age [y:d:h:m:s]: 00:240:12:20:30
Block: 942631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172316 RingCT/type: yes/0
Extra: 01e968f3d179a36d9807a9aed7ba182367364197be90594d39b89a907fcb52d98e0211000000029da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5b779a69eda3986ef986d59428c9817e7377a0e025fc7207fef58ab16e854a8 0.600000000000 1400807 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": 942641, "vin": [ { "gen": { "height": 942631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5b779a69eda3986ef986d59428c9817e7377a0e025fc7207fef58ab16e854a8" } } ], "extra": [ 1, 233, 104, 243, 209, 121, 163, 109, 152, 7, 169, 174, 215, 186, 24, 35, 103, 54, 65, 151, 190, 144, 89, 77, 57, 184, 154, 144, 127, 203, 82, 217, 142, 2, 17, 0, 0, 0, 2, 157, 168, 225, 52, 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