Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48267394fc6a4cdd806c57d98053a987010de3f18888e69d20a67c2aab6f1dd7

Tx prefix hash: 9973a5e5f680753e27e3b1b40e2ac648d20b8d3b9f3e02d1388179daf1000e6d
Tx public key: e42f2a8f10d4687177d6f3bc18830605fb98ecc16a04381d4936cda03f8928da
Timestamp: 1709193530 Timestamp [UCT]: 2024-02-29 07:58:50 Age [y:d:h:m:s]: 01:254:05:41:47
Block: 967973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440426 RingCT/type: yes/0
Extra: 01e42f2a8f10d4687177d6f3bc18830605fb98ecc16a04381d4936cda03f8928da02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51b1a67977e92900e04f8ef0c6741270225f5fbdff2eeb0848c4f51791ffae5c 0.600000000000 1427768 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": 967983, "vin": [ { "gen": { "height": 967973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51b1a67977e92900e04f8ef0c6741270225f5fbdff2eeb0848c4f51791ffae5c" } } ], "extra": [ 1, 228, 47, 42, 143, 16, 212, 104, 113, 119, 214, 243, 188, 24, 131, 6, 5, 251, 152, 236, 193, 106, 4, 56, 29, 73, 54, 205, 160, 63, 137, 40, 218, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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