Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7651293f8e8ad52d19af432ac741e96043ae3715e17477c030374da2704996bf

Tx prefix hash: aad9bac6da1e85f783a5f16b4ce38a292b8d46f0db25025ddb7038523c1ef4bf
Tx public key: ca1bc42bb28757f4a89c1c6e6f063d2d571f86290dee031b042c40d3a0337ac9
Timestamp: 1633257228 Timestamp [UCT]: 2021-10-03 10:33:48 Age [y:d:h:m:s]: 03:227:03:52:40
Block: 345760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 939184 RingCT/type: yes/0
Extra: 01ca1bc42bb28757f4a89c1c6e6f063d2d571f86290dee031b042c40d3a0337ac902110000000afdc024ec000000000000000000

1 output(s) for total of 43.890591403000 dcy

stealth address amount amount idx
00: ea4ccf8946807535d29a4a4827c859d982562d5214777186f9aea3ae83322e86 43.890591403000 709230 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": 345770, "vin": [ { "gen": { "height": 345760 } } ], "vout": [ { "amount": 43890591403, "target": { "key": "ea4ccf8946807535d29a4a4827c859d982562d5214777186f9aea3ae83322e86" } } ], "extra": [ 1, 202, 27, 196, 43, 178, 135, 87, 244, 168, 156, 28, 110, 111, 6, 61, 45, 87, 31, 134, 41, 13, 238, 3, 27, 4, 44, 64, 211, 160, 51, 122, 201, 2, 17, 0, 0, 0, 10, 253, 192, 36, 236, 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