Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63fc47320d8478fa21db60621addba1d1de66661d2aab52b08d2ffbef7e979b3

Tx prefix hash: 9402ca6e99f69e542616e363b7a70393eaf04e6a6bf73c64db31bdc0286b60a1
Tx public key: 3e6fb26a1ca5e8e7e83afe1dc2f5e29ef211471585bb0fb31711271210ce8e77
Timestamp: 1718726176 Timestamp [UCT]: 2024-06-18 15:56:16 Age [y:d:h:m:s]: 00:187:12:37:55
Block: 1046993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134238 RingCT/type: yes/0
Extra: 013e6fb26a1ca5e8e7e83afe1dc2f5e29ef211471585bb0fb31711271210ce8e7702110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1bdbe9b733f6fd78d5201eebc8b2333ba8532cc6d7a0621e689ef450a0e1389 0.600000000000 1516812 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": 1047003, "vin": [ { "gen": { "height": 1046993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1bdbe9b733f6fd78d5201eebc8b2333ba8532cc6d7a0621e689ef450a0e1389" } } ], "extra": [ 1, 62, 111, 178, 106, 28, 165, 232, 231, 232, 58, 254, 29, 194, 245, 226, 158, 242, 17, 71, 21, 133, 187, 15, 179, 23, 17, 39, 18, 16, 206, 142, 119, 2, 17, 0, 0, 0, 8, 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