Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 075e4df73749874e8c6303f96fdd38fccedd62a19c354c8b383b3c6515f2d513

Tx prefix hash: f1091c61b63fa88ec4864ca6f5754dd3d37430bdb596ceb0415797872ddf6a4f
Tx public key: f8dc6e2d07f65a406776f04300d922bf9b8ca9435de615813e8d248d33a38aa8
Timestamp: 1660670182 Timestamp [UCT]: 2022-08-16 17:16:22 Age [y:d:h:m:s]: 02:138:14:50:51
Block: 567250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 620487 RingCT/type: yes/0
Extra: 01f8dc6e2d07f65a406776f04300d922bf9b8ca9435de615813e8d248d33a38aa802110000000165468698000000000000000000

1 output(s) for total of 8.099633731000 dcy

stealth address amount amount idx
00: b6026ae74ffe3c3854528773441d43f424c56eee2145bf8b34331cb1e0027d2e 8.099633731000 1000351 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": 567260, "vin": [ { "gen": { "height": 567250 } } ], "vout": [ { "amount": 8099633731, "target": { "key": "b6026ae74ffe3c3854528773441d43f424c56eee2145bf8b34331cb1e0027d2e" } } ], "extra": [ 1, 248, 220, 110, 45, 7, 246, 90, 64, 103, 118, 240, 67, 0, 217, 34, 191, 155, 140, 169, 67, 93, 230, 21, 129, 62, 141, 36, 141, 51, 163, 138, 168, 2, 17, 0, 0, 0, 1, 101, 70, 134, 152, 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