Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a591fd6219313690907685933485a40a3b43d181129d4f300b538eabfbd08fd3

Tx prefix hash: 63e424a3b4b7193d8902882db2780b78b4c6119ac09084d35629193dd9d61096
Tx public key: 3a4cafe3eae79ac5f1e23361e851c3fa429212a148bba3d21af520e4c3ae92f2
Timestamp: 1709890696 Timestamp [UCT]: 2024-03-08 09:38:16 Age [y:d:h:m:s]: 01:070:11:36:07
Block: 973754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311381 RingCT/type: yes/0
Extra: 013a4cafe3eae79ac5f1e23361e851c3fa429212a148bba3d21af520e4c3ae92f202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfe278773d729a2a595e62a2cbf1d3ddad4c3a80b52e4473d0eb415e4deb8626 0.600000000000 1433693 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": 973764, "vin": [ { "gen": { "height": 973754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfe278773d729a2a595e62a2cbf1d3ddad4c3a80b52e4473d0eb415e4deb8626" } } ], "extra": [ 1, 58, 76, 175, 227, 234, 231, 154, 197, 241, 226, 51, 97, 232, 81, 195, 250, 66, 146, 18, 161, 72, 187, 163, 210, 26, 245, 32, 228, 195, 174, 146, 242, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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