Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc581b468561c562763b36050d1f4d6db436cdadea4a435e6d671aa458cc65be

Tx prefix hash: 6c457403fea235c426e25f5f0cb47ecd5f596f7c838e885fe631e38c4226970f
Tx public key: 871bc55d9f9f0e4797841c4a3234e404a11ca2c5f4c4d4f0683432bacddb31b2
Timestamp: 1701021003 Timestamp [UCT]: 2023-11-26 17:50:03 Age [y:d:h:m:s]: 01:089:20:56:58
Block: 900207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325353 RingCT/type: yes/0
Extra: 01871bc55d9f9f0e4797841c4a3234e404a11ca2c5f4c4d4f0683432bacddb31b2021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.638617034000 dcy

stealth address amount amount idx
00: 54e9a6cf02fdb6fea1ef892ee53e9e4f3a2b552ff97d850195e2a220fa7dcb22 0.638617034000 1356692 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": 900217, "vin": [ { "gen": { "height": 900207 } } ], "vout": [ { "amount": 638617034, "target": { "key": "54e9a6cf02fdb6fea1ef892ee53e9e4f3a2b552ff97d850195e2a220fa7dcb22" } } ], "extra": [ 1, 135, 27, 197, 93, 159, 159, 14, 71, 151, 132, 28, 74, 50, 52, 228, 4, 161, 28, 162, 197, 244, 196, 212, 240, 104, 52, 50, 186, 205, 219, 49, 178, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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