Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05e297a11c3be2ef7b04f476734c8b8cac48fdeaf98d2d656a4c79889f24f26c

Tx prefix hash: 8365fc9c9f89ed13c818c48e838bc837ade80e0cc5e35982b5ca2fd45a325e46
Tx public key: 5354fd0f306f35d4e5002a45c0c00972d0d623ff9f928d68be3851efd1d3b5f6
Timestamp: 1710057888 Timestamp [UCT]: 2024-03-10 08:04:48 Age [y:d:h:m:s]: 01:044:16:31:18
Block: 975142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292920 RingCT/type: yes/0
Extra: 015354fd0f306f35d4e5002a45c0c00972d0d623ff9f928d68be3851efd1d3b5f602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b026d324d4909d8df765846ed2c05811aae20a94934217a59b11b00b50c90a6e 0.600000000000 1435113 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": 975152, "vin": [ { "gen": { "height": 975142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b026d324d4909d8df765846ed2c05811aae20a94934217a59b11b00b50c90a6e" } } ], "extra": [ 1, 83, 84, 253, 15, 48, 111, 53, 212, 229, 0, 42, 69, 192, 192, 9, 114, 208, 214, 35, 255, 159, 146, 141, 104, 190, 56, 81, 239, 209, 211, 181, 246, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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