Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36a50140797aeb4dd21c0b592ee824c01ebb397f5329d53418bd04445572f80f

Tx prefix hash: 56e58b6a7f913471cb26e31f53c04f453bc534383095fb6f16ae88c27b1c68ae
Tx public key: 3729ac1bc5adc06b77a7b6c5325a0cf9ba0ef4dde58e5c39a47de4a9eed6f409
Timestamp: 1723931485 Timestamp [UCT]: 2024-08-17 21:51:25 Age [y:d:h:m:s]: 00:236:08:08:21
Block: 1090159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168784 RingCT/type: yes/0
Extra: 013729ac1bc5adc06b77a7b6c5325a0cf9ba0ef4dde58e5c39a47de4a9eed6f40902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f01fe3fb1ca8d73cc0a42371e55d5e23e83b1e2a72613d24697f77212204b58d 0.600000000000 1564782 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": 1090169, "vin": [ { "gen": { "height": 1090159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f01fe3fb1ca8d73cc0a42371e55d5e23e83b1e2a72613d24697f77212204b58d" } } ], "extra": [ 1, 55, 41, 172, 27, 197, 173, 192, 107, 119, 167, 182, 197, 50, 90, 12, 249, 186, 14, 244, 221, 229, 142, 92, 57, 164, 125, 228, 169, 238, 214, 244, 9, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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