Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d54a5474373635c02adba9114b7bfcdfda00bca60026ac9d3f3c07f2d1ea3199

Tx prefix hash: 91b4a66bb835bfc465315f13117795f533114af111590d462acecb3c832a33a3
Tx public key: 586f92bae5d31a331f18677a79b0c2104cec370ff0f0df05003ca408a6ec921d
Timestamp: 1715005353 Timestamp [UCT]: 2024-05-06 14:22:33 Age [y:d:h:m:s]: 00:334:04:05:06
Block: 1016146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238870 RingCT/type: yes/0
Extra: 01586f92bae5d31a331f18677a79b0c2104cec370ff0f0df05003ca408a6ec921d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86d78b50ef0d8f683d254fbdf4f3e623ae3fa3dbccc705e76c8818c3c5e59979 0.600000000000 1479649 of 15

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": 1016156, "vin": [ { "gen": { "height": 1016146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86d78b50ef0d8f683d254fbdf4f3e623ae3fa3dbccc705e76c8818c3c5e59979" } } ], "extra": [ 1, 88, 111, 146, 186, 229, 211, 26, 51, 31, 24, 103, 122, 121, 176, 194, 16, 76, 236, 55, 15, 240, 240, 223, 5, 0, 60, 164, 8, 166, 236, 146, 29, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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