Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fbfc81492577cb88ef07c6847cc31ab6c7ba46d2b17b7d62519e8d93c483b5e

Tx prefix hash: 0ab5b139a72f82f55a7bd88231d3d6c1248cbfeb3a6fe433aec0f1073345686e
Tx public key: 849f3bca055c196c4dcf70d000a2b0be1e91aa2a49bdacef5253f1994a90b10e
Timestamp: 1681444918 Timestamp [UCT]: 2023-04-14 04:01:58 Age [y:d:h:m:s]: 02:179:01:25:11
Block: 738151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 647809 RingCT/type: yes/0
Extra: 01849f3bca055c196c4dcf70d000a2b0be1e91aa2a49bdacef5253f1994a90b10e021100000004b3164c24000000000000000000

1 output(s) for total of 2.198869911000 dcy

stealth address amount amount idx
00: ba3a6909153680a58b023a04958c1ec40288f82dfcb618029ab826e650bf19af 2.198869911000 1184802 of 0

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": 738161, "vin": [ { "gen": { "height": 738151 } } ], "vout": [ { "amount": 2198869911, "target": { "key": "ba3a6909153680a58b023a04958c1ec40288f82dfcb618029ab826e650bf19af" } } ], "extra": [ 1, 132, 159, 59, 202, 5, 92, 25, 108, 77, 207, 112, 208, 0, 162, 176, 190, 30, 145, 170, 42, 73, 189, 172, 239, 82, 83, 241, 153, 74, 144, 177, 14, 2, 17, 0, 0, 0, 4, 179, 22, 76, 36, 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