Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6698692b58d5cce97afb7bb3ecbd160633c125b12e7ad6615e13679c6b1639f

Tx prefix hash: a217814ec1d0e4168df40b4d8ba4accca631e7c0fd7eccc8ae3a24da77653ce2
Tx public key: fae88022dfe422778e72b3896b5d2c42088cfa9a53d27c42ecf4a3f7b05a909c
Timestamp: 1745743653 Timestamp [UCT]: 2025-04-27 08:47:33 Age [y:d:h:m:s]: 00:207:19:16:49
Block: 1270467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146225 RingCT/type: yes/0
Extra: 01fae88022dfe422778e72b3896b5d2c42088cfa9a53d27c42ecf4a3f7b05a909c0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41ff4af700dbbe830ef1d46892040b54c52fcca6e73595c0ebe6811fa1546f82 0.600000000000 1757710 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": 1270477, "vin": [ { "gen": { "height": 1270467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41ff4af700dbbe830ef1d46892040b54c52fcca6e73595c0ebe6811fa1546f82" } } ], "extra": [ 1, 250, 232, 128, 34, 223, 228, 34, 119, 142, 114, 179, 137, 107, 93, 44, 66, 8, 140, 250, 154, 83, 210, 124, 66, 236, 244, 163, 247, 176, 90, 144, 156, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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