Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9ae0dfe94e1c29f41c2030e743956a874e4ff447120675a87d2bc75706c788c

Tx prefix hash: 46319c9952134302c4885a3538882971cb64044f3b720d45c6da5e1e4d9f1100
Tx public key: b8522e7290cdd89a038e8014270d7820a8ce11b448a42ad1a97ca0acfe08c00c
Timestamp: 1726374012 Timestamp [UCT]: 2024-09-15 04:20:12 Age [y:d:h:m:s]: 01:115:15:30:57
Block: 1110397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341160 RingCT/type: yes/0
Extra: 01b8522e7290cdd89a038e8014270d7820a8ce11b448a42ad1a97ca0acfe08c00c021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5d049b600f40ce5f0a984ce1142eaa95227da3544b4886ed5c7fd2a8c1c75be 0.600000000000 1588990 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": 1110407, "vin": [ { "gen": { "height": 1110397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5d049b600f40ce5f0a984ce1142eaa95227da3544b4886ed5c7fd2a8c1c75be" } } ], "extra": [ 1, 184, 82, 46, 114, 144, 205, 216, 154, 3, 142, 128, 20, 39, 13, 120, 32, 168, 206, 17, 180, 72, 164, 42, 209, 169, 124, 160, 172, 254, 8, 192, 12, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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