Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aed6ad15c10ede631a169addd72b65dc0fb96d42f76375ef39c5c260c37037e

Tx prefix hash: 3ea129a7a30d5c1e773286ac1f014d633880daec5a6fde622c1f475de3b44fe6
Tx public key: 7cd16b039859401df847ef973efe3a8bdc85a86c4f132e4c55b661a16f39bea7
Timestamp: 1717731039 Timestamp [UCT]: 2024-06-07 03:30:39 Age [y:d:h:m:s]: 00:229:22:49:44
Block: 1038755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164507 RingCT/type: yes/0
Extra: 017cd16b039859401df847ef973efe3a8bdc85a86c4f132e4c55b661a16f39bea702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78110152f1e78b5c2d59e56f7016b270d4242b007d1fe6d19639a0db8df418d6 0.600000000000 1507316 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": 1038765, "vin": [ { "gen": { "height": 1038755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78110152f1e78b5c2d59e56f7016b270d4242b007d1fe6d19639a0db8df418d6" } } ], "extra": [ 1, 124, 209, 107, 3, 152, 89, 64, 29, 248, 71, 239, 151, 62, 254, 58, 139, 220, 133, 168, 108, 79, 19, 46, 76, 85, 182, 97, 161, 111, 57, 190, 167, 2, 17, 0, 0, 0, 1, 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