Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f17ae529b9cebbfec5c06937dffcc6b3040b3c98deb5257c840012c438bad68

Tx prefix hash: 14871237e7c3592fe59502484c859bed8f4257a02a7799f32ace2ddcf990bc0a
Tx public key: 3b7eaa7557b2cc331e2d564b3126ecc2e4ad5ca14f5094601c1fc9c82736562f
Timestamp: 1659412234 Timestamp [UCT]: 2022-08-02 03:50:34 Age [y:d:h:m:s]: 03:091:04:59:02
Block: 556837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 844982 RingCT/type: yes/0
Extra: 013b7eaa7557b2cc331e2d564b3126ecc2e4ad5ca14f5094601c1fc9c82736562f02110000000d6570b1ef000000000000000000

1 output(s) for total of 8.769361779000 dcy

stealth address amount amount idx
00: 6447181fbc2ddcf5eb9b002a6e08edf16a57185eae8cd1333e442e846c093d10 8.769361779000 988789 of 0

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": 556847, "vin": [ { "gen": { "height": 556837 } } ], "vout": [ { "amount": 8769361779, "target": { "key": "6447181fbc2ddcf5eb9b002a6e08edf16a57185eae8cd1333e442e846c093d10" } } ], "extra": [ 1, 59, 126, 170, 117, 87, 178, 204, 51, 30, 45, 86, 75, 49, 38, 236, 194, 228, 173, 92, 161, 79, 80, 148, 96, 28, 31, 201, 200, 39, 54, 86, 47, 2, 17, 0, 0, 0, 13, 101, 112, 177, 239, 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