Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1838f0e85a2338b6dfccf0bfa59830d66909f9471668625220a5d1cf4e9ebc12

Tx prefix hash: 5aa0ac95840aac70f4a452acaa16615099e16c37bc7cb8c79c89c34f326e4aa2
Tx public key: 54afbedbe3eca95a79b9ba6a986f2741d1e5a327f152cf02f8c1e69ac7d0b3e0
Timestamp: 1578526079 Timestamp [UCT]: 2020-01-08 23:27:59 Age [y:d:h:m:s]: 05:026:04:20:34
Block: 41677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168556 RingCT/type: yes/0
Extra: 0154afbedbe3eca95a79b9ba6a986f2741d1e5a327f152cf02f8c1e69ac7d0b3e002110000000b8a2ee0d9000000000000000000

1 output(s) for total of 446.604030822000 dcy

stealth address amount amount idx
00: 8657f4d0c6e17b7da0f89e615630971a96fcba9f6aec115d41e2491feb45d4ce 446.604030822000 74466 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": 41687, "vin": [ { "gen": { "height": 41677 } } ], "vout": [ { "amount": 446604030822, "target": { "key": "8657f4d0c6e17b7da0f89e615630971a96fcba9f6aec115d41e2491feb45d4ce" } } ], "extra": [ 1, 84, 175, 190, 219, 227, 236, 169, 90, 121, 185, 186, 106, 152, 111, 39, 65, 209, 229, 163, 39, 241, 82, 207, 2, 248, 193, 230, 154, 199, 208, 179, 224, 2, 17, 0, 0, 0, 11, 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