Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ed0457cea5813b1fab42aa8f592141373700ee2d55ec044f63d632497db934a

Tx prefix hash: f4a41da400bb9cf8e01e514d3fcde8e28ffbaee7f5c0ceb4e68d3a166c08fba9
Tx public key: f4dace315badec23b6f4b16eef6ef854b58881159e35798f1a21b2e5c4c16f17
Timestamp: 1738510610 Timestamp [UCT]: 2025-02-02 15:36:50 Age [y:d:h:m:s]: 00:362:12:14:30
Block: 1210576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256775 RingCT/type: yes/0
Extra: 01f4dace315badec23b6f4b16eef6ef854b58881159e35798f1a21b2e5c4c16f170211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12aadb45f946c30d2a42d075ca98428dff18dfa9a8aa485a8fdd2d89c846c34b 0.600000000000 1697329 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": 1210586, "vin": [ { "gen": { "height": 1210576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12aadb45f946c30d2a42d075ca98428dff18dfa9a8aa485a8fdd2d89c846c34b" } } ], "extra": [ 1, 244, 218, 206, 49, 91, 173, 236, 35, 182, 244, 177, 110, 239, 110, 248, 84, 181, 136, 129, 21, 158, 53, 121, 143, 26, 33, 178, 229, 196, 193, 111, 23, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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