Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f39ee06d766e590c14fc0b9924aff20488f75982e73f13a6bffd025e745bc351

Tx prefix hash: 6499df3f6d813ca9516b1cd539713e61e4c9207b71aece6e5c0a5422f13571f8
Tx public key: 2f7eae1e04eeb89b1d263d80d9b2067548aa514aaaf534f284e26da033b6f20e
Timestamp: 1687468550 Timestamp [UCT]: 2023-06-22 21:15:50 Age [y:d:h:m:s]: 01:250:07:45:38
Block: 788104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440029 RingCT/type: yes/0
Extra: 012f7eae1e04eeb89b1d263d80d9b2067548aa514aaaf534f284e26da033b6f20e02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.502050167000 dcy

stealth address amount amount idx
00: a7e4040023be0d01dec8024905dafaf07a43a1ebcb9b04ff753622893c5bac54 1.502050167000 1238197 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": 788114, "vin": [ { "gen": { "height": 788104 } } ], "vout": [ { "amount": 1502050167, "target": { "key": "a7e4040023be0d01dec8024905dafaf07a43a1ebcb9b04ff753622893c5bac54" } } ], "extra": [ 1, 47, 126, 174, 30, 4, 238, 184, 155, 29, 38, 61, 128, 217, 178, 6, 117, 72, 170, 81, 74, 170, 245, 52, 242, 132, 226, 109, 160, 51, 182, 242, 14, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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