Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a313d1e091dcdef02ba1df95cf47cfb1109e7ede0293eaed320dd108cd120a6a

Tx prefix hash: a2d23ebc4c5ffb49167b6eaac1b3803a2f8aa3b8d54367ba2456efb9e20d7531
Tx public key: 6054d7b57daab2cc7c90ec86a8d59ee5746f7f07d552b67017ae27c680944b0e
Timestamp: 1707001682 Timestamp [UCT]: 2024-02-03 23:08:02 Age [y:d:h:m:s]: 00:346:05:53:15
Block: 949778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247877 RingCT/type: yes/0
Extra: 016054d7b57daab2cc7c90ec86a8d59ee5746f7f07d552b67017ae27c680944b0e02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8274b3a61be219f18a1e0f1838b5cc5dc1150ad4568a13ada8605b51e4737eb 0.600000000000 1408310 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": 949788, "vin": [ { "gen": { "height": 949778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8274b3a61be219f18a1e0f1838b5cc5dc1150ad4568a13ada8605b51e4737eb" } } ], "extra": [ 1, 96, 84, 215, 181, 125, 170, 178, 204, 124, 144, 236, 134, 168, 213, 158, 229, 116, 111, 127, 7, 213, 82, 182, 112, 23, 174, 39, 198, 128, 148, 75, 14, 2, 17, 0, 0, 0, 6, 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