Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 704bd758e79318df2796e5839aafbb6b0785de5278a69d0e50cdecaf17d23099

Tx prefix hash: 2cba62abe7d4d29b33f7ecde3830cf4f6a6f72bd4d151696d3df1c070dcb3a46
Tx public key: 465fba0b58ab2dd94892c1c6d89df9a37d8999864f06a689848fd95d230d05a0
Timestamp: 1716489050 Timestamp [UCT]: 2024-05-23 18:30:50 Age [y:d:h:m:s]: 00:321:03:58:35
Block: 1028456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229534 RingCT/type: yes/0
Extra: 01465fba0b58ab2dd94892c1c6d89df9a37d8999864f06a689848fd95d230d05a002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 171349f9f7c90fefd7de11e7bfce88368269b25bd2a4934fd9b6b3842762fc06 0.600000000000 1496449 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": 1028466, "vin": [ { "gen": { "height": 1028456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "171349f9f7c90fefd7de11e7bfce88368269b25bd2a4934fd9b6b3842762fc06" } } ], "extra": [ 1, 70, 95, 186, 11, 88, 171, 45, 217, 72, 146, 193, 198, 216, 157, 249, 163, 125, 137, 153, 134, 79, 6, 166, 137, 132, 143, 217, 93, 35, 13, 5, 160, 2, 17, 0, 0, 0, 2, 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