Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22b04a475a29d3851317613b2e8daeed3ff8ce156447bc43a86c1d744528b704

Tx prefix hash: c3ae73438871c0214185aaa5b43f787a72fa5ce3112af20900a05aa89144b78d
Tx public key: e5b62ac7cc0966314a794c8d2ba9c1570b79ea69d4710bd6a040f8165af36d3a
Timestamp: 1717961350 Timestamp [UCT]: 2024-06-09 19:29:10 Age [y:d:h:m:s]: 00:304:08:08:40
Block: 1040652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217503 RingCT/type: yes/0
Extra: 01e5b62ac7cc0966314a794c8d2ba9c1570b79ea69d4710bd6a040f8165af36d3a02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4b0efdc7022c1ded61350a1a23bef7d12954351d7128bc2c3a5acb0eea10a00 0.600000000000 1509309 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": 1040662, "vin": [ { "gen": { "height": 1040652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4b0efdc7022c1ded61350a1a23bef7d12954351d7128bc2c3a5acb0eea10a00" } } ], "extra": [ 1, 229, 182, 42, 199, 204, 9, 102, 49, 74, 121, 76, 141, 43, 169, 193, 87, 11, 121, 234, 105, 212, 113, 11, 214, 160, 64, 248, 22, 90, 243, 109, 58, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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