Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70d6c49a6c0220426c6a9ddf9d8d763a2c3d5249cff30a901885e11f16a72cb4

Tx prefix hash: 038691519bbccf62284d6ed0f1365e43460e7b2a9a0e9cdea133d448dd94d2f6
Tx public key: 42bde50ce5a52199d64ba3513b5a68e094aa51f2e28c5615ba82e110476e08ae
Timestamp: 1708661735 Timestamp [UCT]: 2024-02-23 04:15:35 Age [y:d:h:m:s]: 01:271:21:29:49
Block: 963553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453069 RingCT/type: yes/0
Extra: 0142bde50ce5a52199d64ba3513b5a68e094aa51f2e28c5615ba82e110476e08ae02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4720b4f30b300273bec52967fdcb8152c473ac51cbf3ca14af991a457453e9f2 0.600000000000 1423268 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": 963563, "vin": [ { "gen": { "height": 963553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4720b4f30b300273bec52967fdcb8152c473ac51cbf3ca14af991a457453e9f2" } } ], "extra": [ 1, 66, 189, 229, 12, 229, 165, 33, 153, 214, 75, 163, 81, 59, 90, 104, 224, 148, 170, 81, 242, 226, 140, 86, 21, 186, 130, 225, 16, 71, 110, 8, 174, 2, 17, 0, 0, 0, 1, 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