Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3d925c4fd41d2257fda1f958b287caea0661a6c7caa41a928c7411816da77ca

Tx prefix hash: 1aee7f33f300c5c1d58c5c5291bb65945776e9d3e95200256f5dbc7dcd0f0673
Tx public key: 809c7d1ce2ae5c72d2fcc39916bd2bb62ec26103ff3bf173d4dbfbcb18f5bab2
Timestamp: 1577698075 Timestamp [UCT]: 2019-12-30 09:27:55 Age [y:d:h:m:s]: 05:307:02:39:34
Block: 34912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1367004 RingCT/type: yes/0
Extra: 01809c7d1ce2ae5c72d2fcc39916bd2bb62ec26103ff3bf173d4dbfbcb18f5bab20211000000018a2ee0d9000000000000000000

1 output(s) for total of 470.243613966000 dcy

stealth address amount amount idx
00: 00871635b642f77ed29bc64d2daedb93a54eae4dc0ec84ee5590d56d0d30fa62 470.243613966000 58815 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": 34922, "vin": [ { "gen": { "height": 34912 } } ], "vout": [ { "amount": 470243613966, "target": { "key": "00871635b642f77ed29bc64d2daedb93a54eae4dc0ec84ee5590d56d0d30fa62" } } ], "extra": [ 1, 128, 156, 125, 28, 226, 174, 92, 114, 210, 252, 195, 153, 22, 189, 43, 182, 46, 194, 97, 3, 255, 59, 241, 115, 212, 219, 251, 203, 24, 245, 186, 178, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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