Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb064ed90eb5930213c107a856437b8c9da89174e35130086df6dd2b18ffb9c4

Tx prefix hash: b7c10d897b48b8b4597d9f72cb97d0fa684d8f9d76d88b2a9eba6d4b84e6d8e3
Tx public key: e3623d15f8ef0c2c4ad5c0ddb0fdc8a708bfc04990e3e19e42b7b10b935ec167
Timestamp: 1746365005 Timestamp [UCT]: 2025-05-04 13:23:25 Age [y:d:h:m:s]: 00:239:08:58:00
Block: 1275611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168843 RingCT/type: yes/0
Extra: 01e3623d15f8ef0c2c4ad5c0ddb0fdc8a708bfc04990e3e19e42b7b10b935ec1670211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c5205049012d129155c52164b1558aa62dca2cf60413857cff1b6ad8803fb18 0.600000000000 1762926 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": 1275621, "vin": [ { "gen": { "height": 1275611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c5205049012d129155c52164b1558aa62dca2cf60413857cff1b6ad8803fb18" } } ], "extra": [ 1, 227, 98, 61, 21, 248, 239, 12, 44, 74, 213, 192, 221, 176, 253, 200, 167, 8, 191, 192, 73, 144, 227, 225, 158, 66, 183, 177, 11, 147, 94, 193, 103, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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