Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73e422190e513a69b45a1a133ce5263e0d504d50851e58df9efbcf03d0f3e01a

Tx prefix hash: 03373ec0465062f7042f3799a90eb4ea9491fae2ec0d6c89e5aa8b5657925b44
Tx public key: f6b5059aa81b0f85127e7c2104060a1e172b60572734d0371fa72c34e66c5b45
Timestamp: 1703695696 Timestamp [UCT]: 2023-12-27 16:48:16 Age [y:d:h:m:s]: 01:316:19:03:00
Block: 922385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485235 RingCT/type: yes/0
Extra: 01f6b5059aa81b0f85127e7c2104060a1e172b60572734d0371fa72c34e66c5b45021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc838df07d2db852eaa2b9eabf699ec5daea40469b13df87db18b54f01247c94 0.600000000000 1380081 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": 922395, "vin": [ { "gen": { "height": 922385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc838df07d2db852eaa2b9eabf699ec5daea40469b13df87db18b54f01247c94" } } ], "extra": [ 1, 246, 181, 5, 154, 168, 27, 15, 133, 18, 126, 124, 33, 4, 6, 10, 30, 23, 43, 96, 87, 39, 52, 208, 55, 31, 167, 44, 52, 230, 108, 91, 69, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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