Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1afa3507f59347b0bfc1a832020f16e2f43e86805a236b225eeb29df63d07ef

Tx prefix hash: 1af23973a1f8be859422b80e9312f11d9d0f77b02e3f2a4b581d74fa93c34978
Tx public key: 7a98c4d755220bd161a9179a17126886a3295e39d6a1e2f8f812990d3939a66f
Timestamp: 1677145654 Timestamp [UCT]: 2023-02-23 09:47:34 Age [y:d:h:m:s]: 01:322:10:34:12
Block: 703153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491394 RingCT/type: yes/0
Extra: 017a98c4d755220bd161a9179a17126886a3295e39d6a1e2f8f812990d3939a66f02110000000174b6d784000000000000000000

1 output(s) for total of 2.871852476000 dcy

stealth address amount amount idx
00: 39d0afd55323abd4e1aa1ff0f20c01d18d34b0944347c5ca33b43f29e2037ee5 2.871852476000 1146718 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": 703163, "vin": [ { "gen": { "height": 703153 } } ], "vout": [ { "amount": 2871852476, "target": { "key": "39d0afd55323abd4e1aa1ff0f20c01d18d34b0944347c5ca33b43f29e2037ee5" } } ], "extra": [ 1, 122, 152, 196, 215, 85, 34, 11, 209, 97, 169, 23, 154, 23, 18, 104, 134, 163, 41, 94, 57, 214, 161, 226, 248, 248, 18, 153, 13, 57, 57, 166, 111, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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