Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f319e6b0ababb7af297e8825f67f43bbcfab5766017d4503df7213f57d62665

Tx prefix hash: f1ed5341faac4841403d107393833d6b809939fcd1ca78f6e20ea6744562ef50
Tx public key: ae5a5640576fdcf20f05e00f96520e541a0ab2d906a51b50be83aca6cc4ea583
Timestamp: 1705675941 Timestamp [UCT]: 2024-01-19 14:52:21 Age [y:d:h:m:s]: 00:357:23:55:43
Block: 938769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256327 RingCT/type: yes/0
Extra: 01ae5a5640576fdcf20f05e00f96520e541a0ab2d906a51b50be83aca6cc4ea58302110000000182025268000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ed08f32fe4b56fd4d45fd922235d4ad9eab2232b4a0d88d2a07cb040f8139ef 0.600000000000 1396847 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": 938779, "vin": [ { "gen": { "height": 938769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ed08f32fe4b56fd4d45fd922235d4ad9eab2232b4a0d88d2a07cb040f8139ef" } } ], "extra": [ 1, 174, 90, 86, 64, 87, 111, 220, 242, 15, 5, 224, 15, 150, 82, 14, 84, 26, 10, 178, 217, 6, 165, 27, 80, 190, 131, 172, 166, 204, 78, 165, 131, 2, 17, 0, 0, 0, 1, 130, 2, 82, 104, 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