Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8907f6615e04a0f3946562fb3d0b2f3747947e297f7df30034b0844d505992df

Tx prefix hash: af55defd7727720924bfa3f0bb537bc8e83183614bfd65d2747c8011bd152f8e
Tx public key: 648f87ecfb83cb2a978bdc411efd575d09f5dc42ea9a2414fd23f347d6bd0dbe
Timestamp: 1580797790 Timestamp [UCT]: 2020-02-04 06:29:50 Age [y:d:h:m:s]: 04:291:02:19:54
Block: 58512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099194 RingCT/type: yes/0
Extra: 01648f87ecfb83cb2a978bdc411efd575d09f5dc42ea9a2414fd23f347d6bd0dbe02110000007aff58ae94000000000000000000

1 output(s) for total of 392.759117043000 dcy

stealth address amount amount idx
00: 1a31d89a6b789ea22e41f234231718a48174864fd399725c181e9a85a4341b33 392.759117043000 108074 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": 58522, "vin": [ { "gen": { "height": 58512 } } ], "vout": [ { "amount": 392759117043, "target": { "key": "1a31d89a6b789ea22e41f234231718a48174864fd399725c181e9a85a4341b33" } } ], "extra": [ 1, 100, 143, 135, 236, 251, 131, 203, 42, 151, 139, 220, 65, 30, 253, 87, 93, 9, 245, 220, 66, 234, 154, 36, 20, 253, 35, 243, 71, 214, 189, 13, 190, 2, 17, 0, 0, 0, 122, 255, 88, 174, 148, 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