Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16b2dab1338b7e732e7e3b3afa864b9d07a71e23960a85e0eb75f4718ca78679

Tx prefix hash: 0296465d8ccd497966b2e7eb2291e966bfda0a47d0a5f3dd58c5e6a55ef1ad0d
Tx public key: c4c7eba13c614e5f57b310df5c86aa7dfaa78d38c9e5a885f8d3767b191ce6c8
Timestamp: 1725063172 Timestamp [UCT]: 2024-08-31 00:12:52 Age [y:d:h:m:s]: 01:072:22:44:14
Block: 1099531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310572 RingCT/type: yes/0
Extra: 01c4c7eba13c614e5f57b310df5c86aa7dfaa78d38c9e5a885f8d3767b191ce6c802110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7417b53219e3ed10f4d6d7cf728eed6c38cd5456987dcea5a647ec8d393611e2 0.600000000000 1575494 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": 1099541, "vin": [ { "gen": { "height": 1099531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7417b53219e3ed10f4d6d7cf728eed6c38cd5456987dcea5a647ec8d393611e2" } } ], "extra": [ 1, 196, 199, 235, 161, 60, 97, 78, 95, 87, 179, 16, 223, 92, 134, 170, 125, 250, 167, 141, 56, 201, 229, 168, 133, 248, 211, 118, 123, 25, 28, 230, 200, 2, 17, 0, 0, 0, 9, 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