Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 990e7f8d89af17dd25bd652b60a1fed0647f6fd3101289cc1a5a1c21799fa751

Tx prefix hash: e04f17fefccb7c19a4eae16a2124a7a61fc03fdf6afa40ef72ec3c3453a2997c
Tx public key: a7933b1a3fc8b0dc2e30a704d3f3ac69cea10d13bdf889736634194af2a76c0b
Timestamp: 1634295398 Timestamp [UCT]: 2021-10-15 10:56:38 Age [y:d:h:m:s]: 03:076:05:43:56
Block: 353523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 832319 RingCT/type: yes/0
Extra: 01a7933b1a3fc8b0dc2e30a704d3f3ac69cea10d13bdf889736634194af2a76c0b021100000001a272b9cb000000000000000000

1 output(s) for total of 41.364898695000 dcy

stealth address amount amount idx
00: cfde1be889792d46fb757cc0d9f2b9fa3df5a439cffa23aecc9e96017174e9da 41.364898695000 722387 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": 353533, "vin": [ { "gen": { "height": 353523 } } ], "vout": [ { "amount": 41364898695, "target": { "key": "cfde1be889792d46fb757cc0d9f2b9fa3df5a439cffa23aecc9e96017174e9da" } } ], "extra": [ 1, 167, 147, 59, 26, 63, 200, 176, 220, 46, 48, 167, 4, 211, 243, 172, 105, 206, 161, 13, 19, 189, 248, 137, 115, 102, 52, 25, 74, 242, 167, 108, 11, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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